The "hosting cluster" should be used for the Policy, OperatorPolicy, and compliance events
Ref: https://issues.redhat.com/browse/ACM-11255
Signed-off-by: yiraeChristineKim <yikim@redhat.com>
(cherry picked from commit a2ebc6b)

Previously, the operator policy controller would list all InstallPlans
in the subscription namespace and filter down to ones it considered
relevant. Among other things, it used OwnerReferences to do this
filtering, but those are inconsistently applied by OLM.

Now, it only looks at InstallPlans labelled specifically for the
subscription in the policy, which seems to be much more reliably set and
updated by OLM. Generally, only one InstallPlan will have the label,
which makes it more possible to unambiguously assign a compliance to it
based on its phase (previously, it was unclear what to assign to
"historic" InstallPlans).

Much of the controller logic still handles the possibility of there
being multiple relevant InstallPlans, for robustness.

Refs:
 - https://issues.redhat.com/browse/ACM-11025

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
(cherry picked from commit c636d7d)